A Review of Current Heart Failure Apps

Background: Heart disease is the second leading cause of death in Canada, with tremendous economic impacts on the healthcare system. Currently, there are several smartphone based heart failure (HF) apps available for patients. These apps provide information to patients regarding HF, and how to monitor and manage their condition. This review describes the current literature on HF apps, and describes the features offered by these apps. Methods and Results: Peer-reviewed literature was searched and revealed only a limited number of studies (8) related to HF apps, including HeartMapp, SUPPORT-HF and CardioManager.  A Google-based grey literature search was conducted, and Google Play and the Apple Store were also searched to identify additional HF-related apps. These searches revealed several other HF-related apps (total 11), the features of which are described in the current review. Conclusion: This review will help healthcare providers select apps for themselves and recommend HF apps to their patients that provide the most suitable disease and management information and monitoring capability. The insight will also help software developers design apps in the future that will provide better support to patients with HF and help the healthcare providers monitor their condition better

Code Coverage and Test Suite Effectiveness: Empirical Study with Real Bugs in Large Systems

Abstract—During software maintenance, testing is a crucial activity to ensure the quality of program code as it evolves over time. With the increasing size and complexity of software, adequate software testing has become increasingly important. Code coverage is often used as a yardstick to gauge the compre-hensiveness of test cases and the adequacy of testing. A test suite quality is often measured by the number of bugs it can find (aka. kill). Previous studies have analysed the quality of a test suite by its ability to kill mutants, i.e., artificially seeded faults. However, mutants do not necessarily represent real bugs. Moreover, many studies use small programs which increases the threat of the applicability of the results on large real-world systems. In this paper, we analyse two large software systems to measure the relationship of code coverage and its effectiveness in killing real bugs from the software systems. We use Randoop, a random test generation tool to generate test suites with varying levels of coverage and run them to analyse if the test suites can kill each of the real bugs or not. In this preliminary study, we have performed an experiment on 67 and 92 real bugs from Apache HTTPClient and Mozilla Rhino, respectively. Our experiment finds that there is indeed statistically significant correlation between code coverage and bug kill effectiveness. The strengths of the correlation, however, differ for the two software systems. For HTTPClient, the correlation is moderate for both statement and branch coverage. For Rhino, the correlation is strong for both statement and branch coverage

An exploratory study of functionality and learning resources of web APIs on Programmableweb

Ministry of Education, Singapore under its Academic Research Funding Tier

An atypical adenomatoid odontogenic tumour in the mandible: a report of a paediatric case

An adenomatoid odontogenic tumour (AOT) is a rare odontogenic tumour that is often misdiagnosed as an odontogenic cyst. To acquire additional information about AOT, all reports regarding AOT that had been cited in ‘Pub Med’ since 1990 onwards were reviewed. AOT accounts for about 1–9% of all odontogenic tumours. It is predominantly found in young and female patients, is located more often in the maxilla, and in most cases is associated with an unerupted permanent tooth. The differential diagnosis between AOT and other odontogenic tumours such as ameloblastoma should be well made to avoid extensive ablative surgery. However, AOT frequently resembles other odontogenic lesions such as dentigerous cysts or ameloblastoma. Immunohistochemically, AOT is characterized by positive reactions with certain cytokeratins. For illustration a rare case of an AOT in the mandible is presented that had atypical findings such as buccolingual cortical perforation and resorption with displacement of adjoining teeth.Keywords: adenomatoid odontogenic tumor, dentigerous cyst, odontogenic tumor, paediatric cas

mRNA levels are buffered upon knockdown of RNA decay and translation factors via adjustment of transcription rates in human HepG2 cells

Evidence from yeast and mammals argues the existence of cross-talk between transcription and mRNA decay. Stabilization of transcripts upon depletion of mRNA decay factors generally leads to no changes in mRNA abundance, attributing this to decreased transcription rates. We show that knockdown of human XRN1, CNOT6 and ETF1 genes in HepG2 cells led to significant alteration in stability of specific mRNAs, alterations in half-life were inversely associated with transcription rates, mostly not resulting in changes in abundance. We demonstrate the existence of the gene expression buffering mechanism in human cells that responds to both transcript stabilization and destabilization to maintain mRNA abundance via altered transcription rates and may involve translation. We propose that this buffering may hold novel cancer therapeutic targets.</p

Code coverage and postrelease defects: A large-scale study on open source projects

International audienceTesting is a pivotal activity in ensuring the quality of software. Code coverage is a common metric used as a yardstick to measure the efficacy and adequacy of testing. However, does higher coverage actually lead to a decline in post-release bugs? Do files that have higher test coverage actually have fewer bug reports? The direct relationship between code coverage and actual bug reports has not yet been analysed via a comprehensive empirical study on real bugs. Past studies only involve a few software systems or artificially injected bugs (mutants).In this empirical study, we examine these questions in the context of open-source software projects based on their actual reported bugs. We analyze 100 large open-source Java projects and measure the code coverage of the test cases that come along with these projects. We collect real bugs logged in the issue tracking system after the release of the software and analyse the correlations between code coverage and these bugs. We also collect other metrics such as cyclomatic complexity and lines of code, which are used to normalize the number of bugs and coverage to correlate with other metrics as well as use these metrics in regression analysis. Our results show that coverage has an insignificant correlation with the number of bugs that are found after the release of the software at the project level, and no such correlation at the file level

An empirical study of adoption of software testing in open source projects

Abstract—In software engineering, testing is a crucial ac-tivity that is designed to ensure the quality of program code. For this activity, software teams spend substantial resources constructing test cases to thoroughly assess the correctness of software functionality. What is the proportion of open source projects that include test cases? What is the effect of number of developers on the number of test cases? In this study, we explore open source projects and investigate the correlation between the presence of test cases and various project development characteristics, including the number of lines of code, the size of development teams and the quantity of bug reports. The results show that projects with test cases are bigger in size and projects with bigger team sizes have higher number of test cases. However, surprisingly, number of test cases has a weak correlation with the number of bugs. Keywords-Empirical study, Software testing, Adequacy, Test case